Skip to content

feat(vue-hooks): add hooks package packaging logic #2866

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Feb 8, 2025
Merged

Conversation

zzcr
Copy link
Member

@zzcr zzcr commented Feb 7, 2025

PR

添加vue-hooks包构建打包逻辑

PR Checklist

Please check if your PR fulfills the following requirements:

  • The commit message follows our Commit Message Guidelines
  • Tests for the changes have been added (for bug fixes / features)
  • Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

  • Bugfix
  • Feature
  • Code style update (formatting, local variables)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • CI related changes
  • Documentation content changes
  • Other... Please describe:

What is the current behavior?

Issue Number: N/A

What is the new behavior?

Does this PR introduce a breaking change?

  • Yes
  • No

Other information

Summary by CodeRabbit

  • New Features

    • Introduced automated build, testing, and publishing commands to streamline usage and improve reliability for package consumers.
  • Chores

    • Enhanced development tooling with updated TypeScript and bundler configurations, ensuring optimized compilation and a more efficient build process.

Copy link

coderabbitai bot commented Feb 7, 2025

Walkthrough

The pull request updates the Vue Hooks package by modifying its build and testing configurations. In the package.json file, the "module" field is removed; scripts have been updated to include a Vitest test command, along with new build and publish scripts. Additionally, the configuration now explicitly defines the package entry point via a "main" field and introduces devDependencies for development tooling. New TypeScript configuration files (tsconfig.json and tsconfig.node.json) and a Vite configuration file have also been added to streamline compilation and bundling.

Changes

File(s) Change Summary
packages/vue-hooks/package.json Removed "module" field; added "main" (dist/index.js), updated "scripts" (replacing test error, adding build and pub scripts), and added "devDependencies".
packages/vue-hooks/tsconfig.json,
packages/vue-hooks/tsconfig.node.json
New TypeScript configuration files added with enhanced compiler settings, module resolution, and incremental build options.
packages/vue-hooks/vite.config.ts Introduced a new Vite configuration file using defineConfig with the inclusion of the vite-plugin-dts for declaration generation and external dependency settings.

Sequence Diagram(s)

sequenceDiagram
  participant Dev as Developer
  participant PKG as package.json
  participant Vite as Vite Build Process
  participant Plugin as DTS Plugin

  Dev->>PKG: Run "npm run build"
  PKG->>Vite: Execute "vite build"
  Vite->>Plugin: Generate type declarations via vite-plugin-dts
  Vite->>Vite: Bundle library per configuration (external dependencies, input: index.ts)
  Vite-->>PKG: Output bundled files to dist/ (entry: index.js)
  Dev->>PKG: Optionally run "npm run pub" to publish package
Loading

Possibly related PRs

Suggested labels

enhancement, chore

Suggested reviewers

  • kagol

Poem

I'm a bunny with a code delight,
Hopping through scripts both day and night.
With a new build here and tests that sing,
My whiskers twitch at every new thing.
CodeRabbit cheers—let the changes take flight!

✨ Finishing Touches
  • 📝 Generate Docstrings (Beta)

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@github-actions github-actions bot added the enhancement New feature or request (功能增强) label Feb 7, 2025
Copy link

Walkthrough

This PR introduces the packaging logic for the vue-hooks package. It includes configuration changes to support the build process using Vite, along with updates to TypeScript configuration files.

Changes

Files Summary
packages/vue-hooks/package.json Updated to include build scripts and dependencies for the vue-hooks package.
packages/vue-hooks/tsconfig.json, packages/vue-hooks/tsconfig.node.json Added TypeScript configuration files for the vue-hooks package.
packages/vue-hooks/vite.config.ts New Vite configuration file added to define the build process for the vue-hooks package.

Copy link

github-actions bot commented Feb 7, 2025

[e2e-test-warn]
The component to be tested is missing.

The title of the Pull request should look like "fix(vue-renderless): [action-menu, alert] fix xxx bug".

Please make sure you've read our contributing guide

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (2)
packages/vue-hooks/vite.config.ts (2)

1-6: Enhance vite-plugin-dts configuration for better TypeScript support.

The current configuration lacks important options for TypeScript declaration file generation. Consider adding the following configurations to improve type generation:

-  plugins: [dts()],
+  plugins: [
+    dts({
+      tsConfigFilePath: './tsconfig.json',
+      outDir: 'dist/types',
+      skipDiagnostics: false,
+      rollupTypes: true
+    })
+  ],

8-10: Remove redundant entry point configuration.

The entry point 'index.ts' is specified twice in the configuration. This is redundant and could lead to confusion.

    lib: {
-      entry: ['index.ts']
+      entry: 'index.ts'
    },
    rollupOptions: {
      external: [/@opentiny/, /@floating-ui/],
-      input: ['index.ts'],

Also applies to: 13-13

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between f4fcf7a and 59be827.

📒 Files selected for processing (4)
  • packages/vue-hooks/package.json (1 hunks)
  • packages/vue-hooks/tsconfig.json (1 hunks)
  • packages/vue-hooks/tsconfig.node.json (1 hunks)
  • packages/vue-hooks/vite.config.ts (1 hunks)
✅ Files skipped from review due to trivial changes (2)
  • packages/vue-hooks/tsconfig.node.json
  • packages/vue-hooks/tsconfig.json
🔇 Additional comments (5)
packages/vue-hooks/package.json (4)

10-12: Scripts Update: Modernizing Build, Publish, and Test Commands

The new "build", "pub", and "test" scripts are well-defined. Using "vite build" for the build process and "vitest" for testing aligns with a modern Vue/TypeScript workflow. The publish script disables git checks (via --no-git-checks) for streamlined publishing; ensure that this role is acceptable within your release process.


15-16: Publish Configuration Consistency

The "publishConfig" now sets "main" to "dist/index.js" and keeps "access" as "public", which is great for specifying the built entry point when publishing. However, note that the root-level "main" field on line 8 is still set to "index.ts". Maintaining consistency between these two could prevent confusion during module resolution. Consider aligning the root "main" field with the publish configuration if the built output is intended to be consumed.


18-21: Dependency Version Resolution via Workspaces

The dependency "@opentiny/utils" is now specified with "workspace:~". This is a valid approach in a PNPM-managed monorepo; however, please confirm that your tooling reliably resolves this version during the build process.


22-27: Custom Version Specifiers in DevDependencies

The addition of "devDependencies" for "typescript", "vite", "vite-plugin-dts", and "vitest" broadens the tooling base for development and building. The use of custom version specifiers like "catalog:" for "typescript", "vite", and "vitest" is uncommon. Please ensure that these identifiers are intentional, documented, and properly resolved by your package manager. If these values serve as placeholders or custom resolution paths, providing clarity (in comments or documentation) would help maintainability.

packages/vue-hooks/vite.config.ts (1)

7-22: Add missing build configuration options.

Consider adding the following build options to improve the output:

  build: {
+    outDir: 'dist',
+    sourcemap: true,
+    minify: 'esbuild',
    lib: {
      entry: 'index.ts'
    },

Verify external dependencies configuration.

Please ensure all dependencies are correctly marked as external. Run this script to verify:

✅ Verification successful

🏁 Script executed:

#!/bin/bash
# Check package.json for dependencies that should be marked as external
jq -r '.dependencies, .peerDependencies | keys[]' packages/vue-hooks/package.json 2>/dev/null || echo "No package.json found"

# Search for imports in the source code
echo "Imports found in source code:"
rg -t ts "^import.*from.*['\"](@|vue)" packages/vue-hooks/src/

Length of output: 1327


Build configuration enhancements and verified external dependencies

• The external dependencies (@floating-ui/dom and @opentiny/utils) imported in the source code match the regular expressions configured in the Vite config.
• The build configuration, however, is missing optional parameters such as outDir, sourcemap, and minify. Adding these will improve the output as suggested.

@zzcr zzcr merged commit 891f124 into dev Feb 8, 2025
11 checks passed
@kagol kagol deleted the add-hooks-build-0207 branch April 14, 2025 12:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request (功能增强)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant